Fix problem pod could not resolve external domain from upstream dns w…#931
Open
nontster wants to merge 1 commit intorancher:dev-v2.6from
Open
Fix problem pod could not resolve external domain from upstream dns w…#931nontster wants to merge 1 commit intorancher:dev-v2.6from
nontster wants to merge 1 commit intorancher:dev-v2.6from
Conversation
…hen nodelocaldns cache enabled
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When nodelocaldns cache enabled, pod cannot resolve domain outside the Kubernetes cluster using upstream dns due to upstream dns not support TCP.
The force_tcp has to be removed to fix this problem. Please refer to the right configmap from upstream https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L100